<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>3.3. How to import an existing Capella Project</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="How_to_Import_an_Existing_Project_in_a_Workspace.3F">How to Import an Existing Project in a Workspace?</h1>
		<p>
			<br/>
		</p>
		<table border="1">
			<tr>
				<td>
					<p>
						<img height="34" width="32" border="0" src="Images/Flag.jpg"/>
					</p>
				</td>
				<td>
					<p><li>In order to import a Capella project, you need to have the same version as the one used to create / edit the model.</li>
<li>If you have a more recent version, a migration of the project is required.</li>
<li>In any case, a Capella project cannot be open with an older version. If a migration is performed, it will not be possible to open the model with older version anymore.</li>
<li>Finally, you also need to be careful about the extensions (add-ons / viewpoints) used to edit the model.</li>
<li>Some extensions enrich Capella with new concepts or new graphical representations. In this case, it is required to have the same extensions installed in order to be able to open the model.</li>
<li>If not the case, it is possible to perform a model detachment. This detachment will irreversibly delete all the information about the missing extensions.</li></p>
				</td>
			</tr>
		</table>
		<p>
			<br/>
		</p>
		<p>From the Project Explorer, select Import&hellip;</p>
		<p>
			<img border="0" src="Images/3.3.%20How%20to%20import%20an%20existing%20Melody%20Advance%20Project_html_m618030b9.png"/>
		</p>
		<p>In the dialog box, select &ldquo;Existing Projects into Workspace&rdquo;.</p>
		<p>
			<img border="0" src="Images/3.3.%20How%20to%20import%20an%20existing%20Melody%20Advance%20Project_html_m2c1e06a6.png"/>
		</p>
		<p>Then, &ldquo;select archive file&rdquo; if the project you want to import is a zip, or &ldquo;root directory&rdquo; if it is not.</p>
		<p>
			<img border="0" src="Images/3.3.%20How%20to%20import%20an%20existing%20Melody%20Advance%20Project_html_m43239c7f.png"/>
		</p>
		<p>When choosing &ldquo;Select archive file&rdquo;, the following dialog box opens:</p>
		<p>
			<img border="0" src="Images/3.3.%20How%20to%20import%20an%20existing%20Melody%20Advance%20Project_html_78863ecb.png"/>
		</p>
		<p>The archive of the Project will be extracted inside the Workspace (i.e. the physical location of the imported will be the same as the location of the Workspace).</p>
		<p>When choosing &ldquo;Select Root Directory&rdquo;, the following dialog box opens:</p>
		<p>
			<img border="0" src="Images/3.3.%20How%20to%20import%20an%20existing%20Melody%20Advance%20Project_html_1e9ba319.png"/>
		</p>
		<p>For each project in the selected directory, one can select whether the Project should be copied within the Workspace or not.</p>
		<p>When choosing the copy option:</p>
		<ul>
			<li>The original Project will be duplicated in the file system</li>
			<li>Modifications will be applied on the copy inside the Workspace and 	not on the original Project files (see documentation about 	relationships between Projects and Workspaces).</li>
		</ul>
		<p>Click on Finish. The selected projects are opened in the current workspace.</p>
	</body>
</html>